Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f244575c0004889acc52301cfc1019ea5e2eb87c9fb9459623a2eec537cfaa

Tx prefix hash: e50c558ac5e12651c7a7ee639a106c7e1778202b0458ce9ed72f1ac058da9262
Tx public key: 13f0ec5f2c4a90f31cdcd47959714f02dfeb179947fe521c3f547b8b0c693869
Timestamp: 1700617914 Timestamp [UCT]: 2023-11-22 01:51:54 Age [y:d:h:m:s]: 01:155:12:36:36
Block: 896871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372339 RingCT/type: yes/0
Extra: 0113f0ec5f2c4a90f31cdcd47959714f02dfeb179947fe521c3f547b8b0c69386902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.655079571000 dcy

stealth address amount amount idx
00: 6994bb7c9297491af9b81f9dbeec465f0c724c6f02b17a317110abe344bf48b1 0.655079571000 1353216 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": 896881, "vin": [ { "gen": { "height": 896871 } } ], "vout": [ { "amount": 655079571, "target": { "key": "6994bb7c9297491af9b81f9dbeec465f0c724c6f02b17a317110abe344bf48b1" } } ], "extra": [ 1, 19, 240, 236, 95, 44, 74, 144, 243, 28, 220, 212, 121, 89, 113, 79, 2, 223, 235, 23, 153, 71, 254, 82, 28, 63, 84, 123, 139, 12, 105, 56, 105, 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