Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f54518f55290bd5f5511f4cb5245603025604eb0e7792774bc89d7988fe09b6

Tx prefix hash: 3910f96d8ab4ea9c8fe628ca6d88fef60d68a632227d0339aec7b71e2ed99a98
Tx public key: 660c55f97b44c8afa920c59de3652b5c71596916986c0e64c8966e6088c96f4a
Timestamp: 1730329777 Timestamp [UCT]: 2024-10-30 23:09:37 Age [y:d:h:m:s]: 00:180:09:29:23
Block: 1143111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128797 RingCT/type: yes/0
Extra: 01660c55f97b44c8afa920c59de3652b5c71596916986c0e64c8966e6088c96f4a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49b698c0cec3b35c1e96a54200e43366086c6aa53b4ad3011b6a1116a058af3 0.600000000000 1626974 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": 1143121, "vin": [ { "gen": { "height": 1143111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49b698c0cec3b35c1e96a54200e43366086c6aa53b4ad3011b6a1116a058af3" } } ], "extra": [ 1, 102, 12, 85, 249, 123, 68, 200, 175, 169, 32, 197, 157, 227, 101, 43, 92, 113, 89, 105, 22, 152, 108, 14, 100, 200, 150, 110, 96, 136, 201, 111, 74, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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