Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca2c544a1a58ccd853c9efa0dba08a649aad19541972e05c3a9acf1387187c90

Tx prefix hash: 3f1679de9f382567f1dd3d6a21fe2953b1b6f6056da46ab3e5151cd99460c597
Tx public key: 5488883f6babf72b37407b5c4ab0274acb05f38a75f18a51377bc5f3d78a9df4
Timestamp: 1740316749 Timestamp [UCT]: 2025-02-23 13:19:09 Age [y:d:h:m:s]: 00:226:15:59:57
Block: 1225516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159704 RingCT/type: yes/0
Extra: 015488883f6babf72b37407b5c4ab0274acb05f38a75f18a51377bc5f3d78a9df4021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b01d7e009729b1c269e4e8f893237e23e988b7bbb1e39e42f62e57e1b471b8f 0.600000000000 1712381 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": 1225526, "vin": [ { "gen": { "height": 1225516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b01d7e009729b1c269e4e8f893237e23e988b7bbb1e39e42f62e57e1b471b8f" } } ], "extra": [ 1, 84, 136, 136, 63, 107, 171, 247, 43, 55, 64, 123, 92, 74, 176, 39, 74, 203, 5, 243, 138, 117, 241, 138, 81, 55, 123, 197, 243, 215, 138, 157, 244, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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