Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e20b2b315346b4b6364d0448f6748d811f382ce2bb4556946e6da0576d276b43

Tx prefix hash: 5423a61721dfe43f9765ee863f4b73066ee59fc68e546a3304a4a63ccc642aa4
Tx public key: a7ca8ff9006f067e877bf842a5c57db0fc435d939a45c1eb1888cdcca9cbb75e
Timestamp: 1700884428 Timestamp [UCT]: 2023-11-25 03:53:48 Age [y:d:h:m:s]: 01:351:00:18:25
Block: 899070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509766 RingCT/type: yes/0
Extra: 01a7ca8ff9006f067e877bf842a5c57db0fc435d939a45c1eb1888cdcca9cbb75e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.644180914000 dcy

stealth address amount amount idx
00: b94d609e0576c4d911a40911ee2a1f8a705ddc515f384162fe6f045529b7ad67 0.644180914000 1355513 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": 899080, "vin": [ { "gen": { "height": 899070 } } ], "vout": [ { "amount": 644180914, "target": { "key": "b94d609e0576c4d911a40911ee2a1f8a705ddc515f384162fe6f045529b7ad67" } } ], "extra": [ 1, 167, 202, 143, 249, 0, 111, 6, 126, 135, 123, 248, 66, 165, 197, 125, 176, 252, 67, 93, 147, 154, 69, 193, 235, 24, 136, 205, 204, 169, 203, 183, 94, 2, 17, 0, 0, 0, 1, 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