Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71448f888558435c7ed85a6b0583a4df3c165bc166a4f3bf7e2dad9870b7e952

Tx prefix hash: 4ba1f23e33b7d8e9b6dd1f3a36fa4a0d65cd1745ebbfbbfa4b83531fff8d5db4
Tx public key: ee2488942bb171abaa0bb9a5331bccb53d797e22452fb5b524e5c528eefad63d
Timestamp: 1734769029 Timestamp [UCT]: 2024-12-21 08:17:09 Age [y:d:h:m:s]: 00:014:21:37:01
Block: 1179899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10648 RingCT/type: yes/0
Extra: 01ee2488942bb171abaa0bb9a5331bccb53d797e22452fb5b524e5c528eefad63d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad7d5a225bf649e94bdb25b50236bda665422cc33a58a3fc7ab7c20f3af4f006 0.600000000000 1666300 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": 1179909, "vin": [ { "gen": { "height": 1179899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad7d5a225bf649e94bdb25b50236bda665422cc33a58a3fc7ab7c20f3af4f006" } } ], "extra": [ 1, 238, 36, 136, 148, 43, 177, 113, 171, 170, 11, 185, 165, 51, 27, 204, 181, 61, 121, 126, 34, 69, 47, 181, 181, 36, 229, 197, 40, 238, 250, 214, 61, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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