Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286cd31b6fef4020b7a2957cdd30f12335604159409ad7c84cb5a01f476f6cf0

Tx prefix hash: b589caa02d54e1560fd3929e4980b8b34ca64bbf93e61f6d21e0d31e37423a07
Tx public key: 6e48785293b8e45498c84f7f45d2bbdcb267dfd58bc8502d77344a83c097e66e
Timestamp: 1716302159 Timestamp [UCT]: 2024-05-21 14:35:59 Age [y:d:h:m:s]: 00:323:05:51:29
Block: 1026908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231023 RingCT/type: yes/0
Extra: 016e48785293b8e45498c84f7f45d2bbdcb267dfd58bc8502d77344a83c097e66e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a339bc9faaf373909cafa7ae6f8f49a5063f36235f404393b768e734a3d4645a 0.600000000000 1494247 of 15

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": 1026918, "vin": [ { "gen": { "height": 1026908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a339bc9faaf373909cafa7ae6f8f49a5063f36235f404393b768e734a3d4645a" } } ], "extra": [ 1, 110, 72, 120, 82, 147, 184, 228, 84, 152, 200, 79, 127, 69, 210, 187, 220, 178, 103, 223, 213, 139, 200, 80, 45, 119, 52, 74, 131, 192, 151, 230, 110, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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