Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2d16d64a89744b148dc3b4a709795ee2c0636c0ed12e95221abff238e37af4

Tx prefix hash: 4dd24a77648ecc29acb5629e1b67d5c3a25c19d4fec943155c9060fd3e2f53dc
Tx public key: a9278c16c6df77f1ce33ad04ce0398c9f2794bcdf16e05305ebae9e0cf16f899
Timestamp: 1722011864 Timestamp [UCT]: 2024-07-26 16:37:44 Age [y:d:h:m:s]: 00:252:21:43:41
Block: 1074232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180661 RingCT/type: yes/0
Extra: 01a9278c16c6df77f1ce33ad04ce0398c9f2794bcdf16e05305ebae9e0cf16f89902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a3faeb612593ca5472d52159c05734431c0a4d0dbc306c83ca75aadf3731c6 0.600000000000 1546745 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": 1074242, "vin": [ { "gen": { "height": 1074232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a3faeb612593ca5472d52159c05734431c0a4d0dbc306c83ca75aadf3731c6" } } ], "extra": [ 1, 169, 39, 140, 22, 198, 223, 119, 241, 206, 51, 173, 4, 206, 3, 152, 201, 242, 121, 75, 205, 241, 110, 5, 48, 94, 186, 233, 224, 207, 22, 248, 153, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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