Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c42c95070c9932d6f0639fa7332b72ca116df19e00e896343c1d74bfb2f5d67

Tx prefix hash: 670789b4fe9f913b4a83b027cad53c853622598737ab112175a7f7853139daad
Tx public key: 32c9f0b860e6e10a0fc82070789daf9bce97cce87392d15ce0ff93b499f0aa80
Timestamp: 1696498406 Timestamp [UCT]: 2023-10-05 09:33:26 Age [y:d:h:m:s]: 01:100:00:15:33
Block: 862915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332744 RingCT/type: yes/0
Extra: 0132c9f0b860e6e10a0fc82070789daf9bce97cce87392d15ce0ff93b499f0aa80021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.848798160000 dcy

stealth address amount amount idx
00: b5270067bbc7d9a2f50be00801bb8247c5c5c91b2290ec14bd05cba4b20cb757 0.848798160000 1317355 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": 862925, "vin": [ { "gen": { "height": 862915 } } ], "vout": [ { "amount": 848798160, "target": { "key": "b5270067bbc7d9a2f50be00801bb8247c5c5c91b2290ec14bd05cba4b20cb757" } } ], "extra": [ 1, 50, 201, 240, 184, 96, 230, 225, 10, 15, 200, 32, 112, 120, 157, 175, 155, 206, 151, 204, 232, 115, 146, 209, 92, 224, 255, 147, 180, 153, 240, 170, 128, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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