Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf12341332baca3799365b8dda0a3a6751c386332282478ef6a4f5a74176c44b

Tx prefix hash: 4c596950e4a9178d78fa1f22fc0ca720bb8ce8beca2f2394b0e22f4d55336fda
Tx public key: bc700dc3c26ea679c9af860d2ae6d1f1d98a2ac013c8a7304a719b635532dc87
Timestamp: 1703632739 Timestamp [UCT]: 2023-12-26 23:18:59 Age [y:d:h:m:s]: 01:095:14:36:38
Block: 921866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329436 RingCT/type: yes/0
Extra: 01bc700dc3c26ea679c9af860d2ae6d1f1d98a2ac013c8a7304a719b635532dc870211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ba59d536937bbb2b5acf84a56540e0ff9dc039cb83f7f2000c95759a05dcae7 0.600000000000 1379560 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": 921876, "vin": [ { "gen": { "height": 921866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ba59d536937bbb2b5acf84a56540e0ff9dc039cb83f7f2000c95759a05dcae7" } } ], "extra": [ 1, 188, 112, 13, 195, 194, 110, 166, 121, 201, 175, 134, 13, 42, 230, 209, 241, 217, 138, 42, 192, 19, 200, 167, 48, 74, 113, 155, 99, 85, 50, 220, 135, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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