Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2215da110bc2542f39f9943b9bfd67d2df1b1290f7b3f92ab423c84ea6d27582

Tx prefix hash: de45584805352978aed88dc3c039532231d6b4901ab8e9cba8ec66952e8f5e5e
Tx public key: f5a6188a46adee238f32094bc408c5001e0b7390da0d7e3136664cf7b834ea51
Timestamp: 1721331849 Timestamp [UCT]: 2024-07-18 19:44:09 Age [y:d:h:m:s]: 00:247:05:53:54
Block: 1068616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176602 RingCT/type: yes/0
Extra: 01f5a6188a46adee238f32094bc408c5001e0b7390da0d7e3136664cf7b834ea51021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 270c72ef3faaf657aa4cb7389b51811dc53d9d7ca91fa3a7143e3eec02255eb9 0.600000000000 1539713 of 15

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": 1068626, "vin": [ { "gen": { "height": 1068616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "270c72ef3faaf657aa4cb7389b51811dc53d9d7ca91fa3a7143e3eec02255eb9" } } ], "extra": [ 1, 245, 166, 24, 138, 70, 173, 238, 35, 143, 50, 9, 75, 196, 8, 197, 0, 30, 11, 115, 144, 218, 13, 126, 49, 54, 102, 76, 247, 184, 52, 234, 81, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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