Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e01f7d4215701f1847ef2b79f5a23da64b0fe90734ac6e01eb51e8ac705528

Tx prefix hash: 40710563c9841419a39a66eed64345878a0dd8d3bca8287e35326c6b8f46db4d
Tx public key: e8877649ad1bd0ce0eb3caeabceb4c9b67467bad3aceea7131c6476d47f0a1ec
Timestamp: 1696091295 Timestamp [UCT]: 2023-09-30 16:28:15 Age [y:d:h:m:s]: 01:187:16:31:13
Block: 859544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395196 RingCT/type: yes/0
Extra: 01e8877649ad1bd0ce0eb3caeabceb4c9b67467bad3aceea7131c6476d47f0a1ec0211000000094b8f5122000000000000000000

1 output(s) for total of 0.870941363000 dcy

stealth address amount amount idx
00: 95514e799d2aa4c0e770ea009c263f82aa4e99fc1ff45d0f125000a8f317857c 0.870941363000 1313774 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": 859554, "vin": [ { "gen": { "height": 859544 } } ], "vout": [ { "amount": 870941363, "target": { "key": "95514e799d2aa4c0e770ea009c263f82aa4e99fc1ff45d0f125000a8f317857c" } } ], "extra": [ 1, 232, 135, 118, 73, 173, 27, 208, 206, 14, 179, 202, 234, 188, 235, 76, 155, 103, 70, 123, 173, 58, 206, 234, 113, 49, 198, 71, 109, 71, 240, 161, 236, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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