Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f832f58f722edfc939c39faf8d157173033a63ea155b6e64bc3ff92a40b3834

Tx prefix hash: 7167a5e0c1e8ea7cef03ed744a38afa3ae0ac141ecb254a45d20d436aaab4cd7
Tx public key: 6b17221b40f816dcb6a37e5b58cb2eb52d97a5ea81405950010791b78caab6b4
Timestamp: 1737132167 Timestamp [UCT]: 2025-01-17 16:42:47 Age [y:d:h:m:s]: 00:153:05:08:32
Block: 1199438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109189 RingCT/type: yes/0
Extra: 016b17221b40f816dcb6a37e5b58cb2eb52d97a5ea81405950010791b78caab6b40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 153a68f400c454042160a09b4b44d77697ee885266346222e1ca4b546066c243 0.600000000000 1686069 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": 1199448, "vin": [ { "gen": { "height": 1199438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "153a68f400c454042160a09b4b44d77697ee885266346222e1ca4b546066c243" } } ], "extra": [ 1, 107, 23, 34, 27, 64, 248, 22, 220, 182, 163, 126, 91, 88, 203, 46, 181, 45, 151, 165, 234, 129, 64, 89, 80, 1, 7, 145, 183, 140, 170, 182, 180, 2, 17, 0, 0, 0, 3, 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