Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8556536f2b78430949a0c1557fe2e68aa9a194dba221e2dea782c834f232715

Tx prefix hash: d9fa40db3ab8721ec51a0f6620edd9c541c0cdd67f4dd15c6289fc8601a1c42b
Tx public key: 1d27b198af22f1424f6b5bb920f28f9c08ef9a27ea886672f2b917193472212b
Timestamp: 1734116576 Timestamp [UCT]: 2024-12-13 19:02:56 Age [y:d:h:m:s]: 00:137:19:07:23
Block: 1174500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98271 RingCT/type: yes/0
Extra: 011d27b198af22f1424f6b5bb920f28f9c08ef9a27ea886672f2b917193472212b021100000001e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2df199f0ea514c4ba941806e09abff0b490696000d179d30a47cccdbedd3ddd 0.600000000000 1660659 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": 1174510, "vin": [ { "gen": { "height": 1174500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2df199f0ea514c4ba941806e09abff0b490696000d179d30a47cccdbedd3ddd" } } ], "extra": [ 1, 29, 39, 177, 152, 175, 34, 241, 66, 79, 107, 91, 185, 32, 242, 143, 156, 8, 239, 154, 39, 234, 136, 102, 114, 242, 185, 23, 25, 52, 114, 33, 43, 2, 17, 0, 0, 0, 1, 232, 144, 243, 105, 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