Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f58cd96c20fcf1e10a687ea86edb970ffb53987bd4ef3588e2fc236cfe160327

Tx prefix hash: 531d7d54279154663e58c5692cb446a02a2c1f404b671d966a610ce16e9e3436
Tx public key: 51f155628cbe8c0719c507e801db26fa0875cb5bff0ccc312ce3a64f1babec7f
Timestamp: 1665167272 Timestamp [UCT]: 2022-10-07 18:27:52 Age [y:d:h:m:s]: 02:181:14:37:08
Block: 604094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651356 RingCT/type: yes/0
Extra: 0151f155628cbe8c0719c507e801db26fa0875cb5bff0ccc312ce3a64f1babec7f02110000000475e3f0e9000000000000000000

1 output(s) for total of 6.114850738000 dcy

stealth address amount amount idx
00: 7ff34563af26e595a5f499ceb20969a8feb460514d09bfc63d5093dec51e63a0 6.114850738000 1040381 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 604104, "vin": [ { "gen": { "height": 604094 } } ], "vout": [ { "amount": 6114850738, "target": { "key": "7ff34563af26e595a5f499ceb20969a8feb460514d09bfc63d5093dec51e63a0" } } ], "extra": [ 1, 81, 241, 85, 98, 140, 190, 140, 7, 25, 197, 7, 232, 1, 219, 38, 250, 8, 117, 203, 91, 255, 12, 204, 49, 44, 227, 166, 79, 27, 171, 236, 127, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8