Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba0222ba2092d452cd1e724ce48891c7de1c5faf4235df06a8baddff89342cb

Tx prefix hash: 60672e04db18a477d12f111d4e1cdd9f16a77e81a3e1099a6ace0e0adeda1dcc
Tx public key: 553a230db54599bfeff2dbc5c3a4824ee9a682fa8f49b05919b764b6d1839ab4
Timestamp: 1701882502 Timestamp [UCT]: 2023-12-06 17:08:22 Age [y:d:h:m:s]: 01:041:17:44:08
Block: 907344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291202 RingCT/type: yes/0
Extra: 01553a230db54599bfeff2dbc5c3a4824ee9a682fa8f49b05919b764b6d1839ab402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.604773349000 dcy

stealth address amount amount idx
00: bc7fbc2caac989e22f19fbea4305c5b18d36c0163876861c3305f18bb008b5c7 0.604773349000 1364327 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": 907354, "vin": [ { "gen": { "height": 907344 } } ], "vout": [ { "amount": 604773349, "target": { "key": "bc7fbc2caac989e22f19fbea4305c5b18d36c0163876861c3305f18bb008b5c7" } } ], "extra": [ 1, 85, 58, 35, 13, 181, 69, 153, 191, 239, 242, 219, 197, 195, 164, 130, 78, 233, 166, 130, 250, 143, 73, 176, 89, 25, 183, 100, 182, 209, 131, 154, 180, 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