Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab7a76c5d8ae7814080ab2cd3df2f1c253988280bdcd41a4bb7b6187214b0ba

Tx prefix hash: 26facaf6d6c679b0ade2ed177fdacbf461a2b9a6d371e77fdeda3bcfe5e1d7b2
Tx public key: afb37b3f3a77d5e171db1875fb98a715059142c5c0f33186906e0952764b3383
Timestamp: 1735376124 Timestamp [UCT]: 2024-12-28 08:55:24 Age [y:d:h:m:s]: 00:097:02:26:00
Block: 1184904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69184 RingCT/type: yes/0
Extra: 01afb37b3f3a77d5e171db1875fb98a715059142c5c0f33186906e0952764b3383021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c88d9b312ad58f167312ad44b539fe9c1efcef7270929038bbe31f8bd0e9b48 0.600000000000 1671367 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": 1184914, "vin": [ { "gen": { "height": 1184904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c88d9b312ad58f167312ad44b539fe9c1efcef7270929038bbe31f8bd0e9b48" } } ], "extra": [ 1, 175, 179, 123, 63, 58, 119, 213, 225, 113, 219, 24, 117, 251, 152, 167, 21, 5, 145, 66, 197, 192, 243, 49, 134, 144, 110, 9, 82, 118, 75, 51, 131, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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