Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56cc4e0d874742c9f465c76560365a1743472dc7d1ab513f525d0680df264d95

Tx prefix hash: 091eba63a955b6d9bf5c942d8883f4221a406ca989cef0a9cc08cdb3b7d87958
Tx public key: 8b3937fe058ee5466f8ee2ffbfb66bc9fc68a71f3d4cf63cd6a6011a137ccb9f
Timestamp: 1719733790 Timestamp [UCT]: 2024-06-30 07:49:50 Age [y:d:h:m:s]: 00:291:00:01:10
Block: 1055342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207938 RingCT/type: yes/0
Extra: 018b3937fe058ee5466f8ee2ffbfb66bc9fc68a71f3d4cf63cd6a6011a137ccb9f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87638976d0431787f36b042d813ea7f798a7fac7dc3f56a59345c6eb50d3accd 0.600000000000 1525741 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": 1055352, "vin": [ { "gen": { "height": 1055342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87638976d0431787f36b042d813ea7f798a7fac7dc3f56a59345c6eb50d3accd" } } ], "extra": [ 1, 139, 57, 55, 254, 5, 142, 229, 70, 111, 142, 226, 255, 191, 182, 107, 201, 252, 104, 167, 31, 61, 76, 246, 60, 214, 166, 1, 26, 19, 124, 203, 159, 2, 17, 0, 0, 0, 3, 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