Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9281767dfdcb09b410df06746339d822833b714e4193b1991a2c754ad39715

Tx prefix hash: c76c4cc4fbd3ad216b7ff9e7770ead7807ed1eaf7d19effd2b68f03dbe9b518f
Tx public key: 347127a489bd3d9c3c1f2fe31ef229a60754190261f0816cee7cb7b01bcb9fff
Timestamp: 1711411062 Timestamp [UCT]: 2024-03-25 23:57:42 Age [y:d:h:m:s]: 01:227:20:17:31
Block: 986374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421500 RingCT/type: yes/0
Extra: 01347127a489bd3d9c3c1f2fe31ef229a60754190261f0816cee7cb7b01bcb9fff02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 466f8f7413ee4ff1c40c3bfde46c0938d66656b9ef722c952592b6f98e2a8ec5 0.600000000000 1446603 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": 986384, "vin": [ { "gen": { "height": 986374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "466f8f7413ee4ff1c40c3bfde46c0938d66656b9ef722c952592b6f98e2a8ec5" } } ], "extra": [ 1, 52, 113, 39, 164, 137, 189, 61, 156, 60, 31, 47, 227, 30, 242, 41, 166, 7, 84, 25, 2, 97, 240, 129, 108, 238, 124, 183, 176, 27, 203, 159, 255, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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