Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973e761d60522570468a657b4bd2860175c529eb12f9053c46f756d28562add5

Tx prefix hash: 414e30a6b3657612ae7325c98f59ad9485377a889ec007c4aa47b4438c1879c9
Tx public key: 13e98a11b1e14542424c71aa0f9e83a8c7d2e8be8cad518ea32e0480f9fe729e
Timestamp: 1652321945 Timestamp [UCT]: 2022-05-12 02:19:05 Age [y:d:h:m:s]: 02:204:05:06:24
Block: 499118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 666436 RingCT/type: yes/0
Extra: 0113e98a11b1e14542424c71aa0f9e83a8c7d2e8be8cad518ea32e0480f9fe729e0211000000024da16a3a000000000000000000

1 output(s) for total of 13.621190884000 dcy

stealth address amount amount idx
00: 4cb4a3654b03e0fd3d0b84bd6860b3f8aa4918d9ab2d02c4a7faee50968e5e2b 13.621190884000 923369 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": 499128, "vin": [ { "gen": { "height": 499118 } } ], "vout": [ { "amount": 13621190884, "target": { "key": "4cb4a3654b03e0fd3d0b84bd6860b3f8aa4918d9ab2d02c4a7faee50968e5e2b" } } ], "extra": [ 1, 19, 233, 138, 17, 177, 225, 69, 66, 66, 76, 113, 170, 15, 158, 131, 168, 199, 210, 232, 190, 140, 173, 81, 142, 163, 46, 4, 128, 249, 254, 114, 158, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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