Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b505863a5db8a56605fd9c5cfbd28509eaefd7274c4cedee0a439f67689d8ff0

Tx prefix hash: f79a47dd6abdd67ee1f71b8fde0ea8e0e2098ea7735b0828997f0086e725149f
Tx public key: 2b37ce570bb39d6a151a563b6f2777b4681ee0181f30c965ee707727f1ef1dc8
Timestamp: 1705428241 Timestamp [UCT]: 2024-01-16 18:04:01 Age [y:d:h:m:s]: 01:039:18:30:58
Block: 936729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289486 RingCT/type: yes/0
Extra: 012b37ce570bb39d6a151a563b6f2777b4681ee0181f30c965ee707727f1ef1dc80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b4c9a9781e1dc46335ca09ef060e1d6dfc46532f1a4cf45bcdf8624778c3e6a 0.600000000000 1394767 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": 936739, "vin": [ { "gen": { "height": 936729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b4c9a9781e1dc46335ca09ef060e1d6dfc46532f1a4cf45bcdf8624778c3e6a" } } ], "extra": [ 1, 43, 55, 206, 87, 11, 179, 157, 106, 21, 26, 86, 59, 111, 39, 119, 180, 104, 30, 224, 24, 31, 48, 201, 101, 238, 112, 119, 39, 241, 239, 29, 200, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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