Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f00c0dd713c14f2d120537d92650d2d634753fad570e4d7e57d58cbe888739c

Tx prefix hash: 374026bb418fd14334122d097b234e047f8b0a993ee2afc4c5bc8d78584fe6f3
Tx public key: 96ba1ab6cfda93c3dc1bc2b0216b17f195a0a0f16dc57bda41e5df8a8f62b8ec
Timestamp: 1712233107 Timestamp [UCT]: 2024-04-04 12:18:27 Age [y:d:h:m:s]: 00:238:07:01:43
Block: 993136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170619 RingCT/type: yes/0
Extra: 0196ba1ab6cfda93c3dc1bc2b0216b17f195a0a0f16dc57bda41e5df8a8f62b8ec0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696b847a329d1cf48dec22ffc1730f1db0fb47613c74bf41774db8f37481365f 0.600000000000 1453518 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": 993146, "vin": [ { "gen": { "height": 993136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696b847a329d1cf48dec22ffc1730f1db0fb47613c74bf41774db8f37481365f" } } ], "extra": [ 1, 150, 186, 26, 182, 207, 218, 147, 195, 220, 27, 194, 176, 33, 107, 23, 241, 149, 160, 160, 241, 109, 197, 123, 218, 65, 229, 223, 138, 143, 98, 184, 236, 2, 17, 0, 0, 0, 6, 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