Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77bbd495b46bdfaf6f3f5c1806f2c04115036118a9fa6179541570afc6b92d6

Tx prefix hash: 5b811edbcb6399f174fbf81acf359cb9edf6efcf65394b5e190506801e88a303
Tx public key: 55c31857f8c91210f7eb279e4b7949dbf68b1a73a3ecda6439bc38df3fc36cf2
Timestamp: 1732596301 Timestamp [UCT]: 2024-11-26 04:45:01 Age [y:d:h:m:s]: 00:202:06:36:28
Block: 1161883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144323 RingCT/type: yes/0
Extra: 0155c31857f8c91210f7eb279e4b7949dbf68b1a73a3ecda6439bc38df3fc36cf2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34563187a09ca4c81925c9f06a5d3a1602e3154c52f87167a2fd91d28a512886 0.600000000000 1647538 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": 1161893, "vin": [ { "gen": { "height": 1161883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34563187a09ca4c81925c9f06a5d3a1602e3154c52f87167a2fd91d28a512886" } } ], "extra": [ 1, 85, 195, 24, 87, 248, 201, 18, 16, 247, 235, 39, 158, 75, 121, 73, 219, 246, 139, 26, 115, 163, 236, 218, 100, 57, 188, 56, 223, 63, 195, 108, 242, 2, 17, 0, 0, 0, 2, 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