Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dfe429ebe5eac310c5dc7fcb65b6f8500da72410934691db0e4aaf4b7d12d39

Tx prefix hash: 44da93277c1c8aa634a5a2b6c04f62a9a7b4f56ec9bbcff16a39fc358258aecb
Tx public key: 8f27ab822e5a1afdf3d9ee5d9500abf21b18db764cd40f698632d1299932822a
Timestamp: 1694236227 Timestamp [UCT]: 2023-09-09 05:10:27 Age [y:d:h:m:s]: 01:173:12:49:41
Block: 844135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385107 RingCT/type: yes/0
Extra: 018f27ab822e5a1afdf3d9ee5d9500abf21b18db764cd40f698632d1299932822a021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.979558535000 dcy

stealth address amount amount idx
00: f89a4b6225d9f0b57f5439b6dc476df7010e8fbc86463fde2be2691cac27bbcf 0.979558535000 1297425 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": 844145, "vin": [ { "gen": { "height": 844135 } } ], "vout": [ { "amount": 979558535, "target": { "key": "f89a4b6225d9f0b57f5439b6dc476df7010e8fbc86463fde2be2691cac27bbcf" } } ], "extra": [ 1, 143, 39, 171, 130, 46, 90, 26, 253, 243, 217, 238, 93, 149, 0, 171, 242, 27, 24, 219, 118, 76, 212, 15, 105, 134, 50, 209, 41, 153, 50, 130, 42, 2, 17, 0, 0, 0, 5, 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