Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cea793ecf35e72c684d309234cbe604b470c9b9c61819785f7a7f865938846e

Tx prefix hash: 824e586142eb03ae2c26cb53defb7fb3fb09ccc5f3f1530114c1c99d3da6aaa0
Tx public key: ba6688f4dbb57b249cb20ffcd31f9512e52dfebef3b52f08fd927aeb02c786eb
Timestamp: 1698661539 Timestamp [UCT]: 2023-10-30 10:25:39 Age [y:d:h:m:s]: 01:151:01:15:59
Block: 880867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368945 RingCT/type: yes/0
Extra: 01ba6688f4dbb57b249cb20ffcd31f9512e52dfebef3b52f08fd927aeb02c786eb02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.740153803000 dcy

stealth address amount amount idx
00: e7ed4203917d38c732cf3b7988bd6b725c7cc9a5c5de5153df7c63c8f3d7e7c1 0.740153803000 1336437 of 0

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": 880877, "vin": [ { "gen": { "height": 880867 } } ], "vout": [ { "amount": 740153803, "target": { "key": "e7ed4203917d38c732cf3b7988bd6b725c7cc9a5c5de5153df7c63c8f3d7e7c1" } } ], "extra": [ 1, 186, 102, 136, 244, 219, 181, 123, 36, 156, 178, 15, 252, 211, 31, 149, 18, 229, 45, 254, 190, 243, 181, 47, 8, 253, 146, 122, 235, 2, 199, 134, 235, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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