Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891fdd14158c0790732981c3e4bdf0272bcfe2fe8fb7020fad4b7faf33e22b31

Tx prefix hash: aa8feb6f0f47cb1ab29be4e766042b7dfac40ecc23fa75a04e961979cdfbf9b1
Tx public key: 28128be0fe9ba18e05254305a56012d8a97dbc4f55fd0fef2b72c0e34404e366
Timestamp: 1710395035 Timestamp [UCT]: 2024-03-14 05:43:55 Age [y:d:h:m:s]: 01:019:03:19:50
Block: 977939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274644 RingCT/type: yes/0
Extra: 0128128be0fe9ba18e05254305a56012d8a97dbc4f55fd0fef2b72c0e34404e3660211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ee6eef688cf5ad0b39cdd23f0bdf531629bf08978d4d441a83ecb7a28f4df24 0.600000000000 1437948 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": 977949, "vin": [ { "gen": { "height": 977939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ee6eef688cf5ad0b39cdd23f0bdf531629bf08978d4d441a83ecb7a28f4df24" } } ], "extra": [ 1, 40, 18, 139, 224, 254, 155, 161, 142, 5, 37, 67, 5, 165, 96, 18, 216, 169, 125, 188, 79, 85, 253, 15, 239, 43, 114, 192, 227, 68, 4, 227, 102, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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