Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 676cf884b3ebdcbb7cf0956c23def4d5cdd07732add41723497bfecd81bd7555

Tx prefix hash: 9da39d5dca8794032805d31776cdcf125d54b1d326cd1d55fa28a29cd4a92e7d
Tx public key: 16aaef2ab5abed61c716a033b9df8ad7d17d115b47e73806a91c4d6abc086e33
Timestamp: 1734887736 Timestamp [UCT]: 2024-12-22 17:15:36 Age [y:d:h:m:s]: 00:326:06:29:31
Block: 1180895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230677 RingCT/type: yes/0
Extra: 0116aaef2ab5abed61c716a033b9df8ad7d17d115b47e73806a91c4d6abc086e330211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f67a01374ba708805960a3ada91c3182a7cdf9b3c39d4e9f4064855f2f96ea64 0.600000000000 1667310 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": 1180905, "vin": [ { "gen": { "height": 1180895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f67a01374ba708805960a3ada91c3182a7cdf9b3c39d4e9f4064855f2f96ea64" } } ], "extra": [ 1, 22, 170, 239, 42, 181, 171, 237, 97, 199, 22, 160, 51, 185, 223, 138, 215, 209, 125, 17, 91, 71, 231, 56, 6, 169, 28, 77, 106, 188, 8, 110, 51, 2, 17, 0, 0, 0, 9, 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