Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2be25bb9d19b3c84c0908be0135cb2693d8e0d9667bc94d0d473c74046622f5b

Tx prefix hash: c6d1caa9e5c7d0792f7581dfdb743331ee0e6c111d94452b885101bb71c5dc6a
Tx public key: 2552cfc1dd31f816e48bc282fe59500868e87bfe364bc2c48a83f0002d165d5c
Timestamp: 1730889790 Timestamp [UCT]: 2024-11-06 10:43:10 Age [y:d:h:m:s]: 00:000:22:12:35
Block: 1147746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 674 RingCT/type: yes/0
Extra: 012552cfc1dd31f816e48bc282fe59500868e87bfe364bc2c48a83f0002d165d5c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8d269342f753c8ebd8dade6afefc61328101b1e8019b6468e7b05b04f192536 0.600000000000 1632447 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": 1147756, "vin": [ { "gen": { "height": 1147746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8d269342f753c8ebd8dade6afefc61328101b1e8019b6468e7b05b04f192536" } } ], "extra": [ 1, 37, 82, 207, 193, 221, 49, 248, 22, 228, 139, 194, 130, 254, 89, 80, 8, 104, 232, 123, 254, 54, 75, 194, 196, 138, 131, 240, 0, 45, 22, 93, 92, 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