Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8aeee366a6c4015428f8e805abf1c67cd9e9025f1cc6e9492483f17d00ceffb

Tx prefix hash: 6d7301ce2a3d74e482fe9b23f294e60746315a408a83ba0babbb1d0ae86c556c
Tx public key: 37edcf4dd81b650e05af659043fc42703aa529f1f1f6d7affe9dea548ca80f0b
Timestamp: 1727067994 Timestamp [UCT]: 2024-09-23 05:06:34 Age [y:d:h:m:s]: 00:121:14:09:29
Block: 1116154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86896 RingCT/type: yes/0
Extra: 0137edcf4dd81b650e05af659043fc42703aa529f1f1f6d7affe9dea548ca80f0b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1980f1775fba4c6a089bb7640910b8e070ae850082ff7fe8fea89cbf32acef 0.600000000000 1596537 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": 1116164, "vin": [ { "gen": { "height": 1116154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1980f1775fba4c6a089bb7640910b8e070ae850082ff7fe8fea89cbf32acef" } } ], "extra": [ 1, 55, 237, 207, 77, 216, 27, 101, 14, 5, 175, 101, 144, 67, 252, 66, 112, 58, 165, 41, 241, 241, 246, 215, 175, 254, 157, 234, 84, 140, 168, 15, 11, 2, 17, 0, 0, 0, 7, 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