Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a44d0242b29d1c6a6a5bfca25c6bb87e44b1040c83e321a909d9410fdc0bd5b

Tx prefix hash: 5507ca1f81aa842d70ef19d66b1d3ba0468b62c6b793844c019463f1ef73f2d6
Tx public key: dc72a0db6949b5c6bf76b3169f231ef2219752a347dd0f43a1f6772cc9eedbd9
Timestamp: 1696484880 Timestamp [UCT]: 2023-10-05 05:48:00 Age [y:d:h:m:s]: 02:040:12:38:10
Block: 862802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548604 RingCT/type: yes/0
Extra: 01dc72a0db6949b5c6bf76b3169f231ef2219752a347dd0f43a1f6772cc9eedbd9021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.849530246000 dcy

stealth address amount amount idx
00: ae996495a15f6c3be7065a4e4a2550c7e8d449fd0682a0996c74a3aca69c54ae 0.849530246000 1317240 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": 862812, "vin": [ { "gen": { "height": 862802 } } ], "vout": [ { "amount": 849530246, "target": { "key": "ae996495a15f6c3be7065a4e4a2550c7e8d449fd0682a0996c74a3aca69c54ae" } } ], "extra": [ 1, 220, 114, 160, 219, 105, 73, 181, 198, 191, 118, 179, 22, 159, 35, 30, 242, 33, 151, 82, 163, 71, 221, 15, 67, 161, 246, 119, 44, 201, 238, 219, 217, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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