Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d70a38c6c6f8d89e8b723e4c02f158d639f191db625316c8d99855d50e4a9c3

Tx prefix hash: 1cab38b4dd70c27b6e5cc12496f2f84eb827e83d6dfdc0a464a1811be4527f31
Tx public key: 931854c7e0942672defd4f63ebf852d26aabb3b4a25473a329dc61a8b7e674b2
Timestamp: 1581692958 Timestamp [UCT]: 2020-02-14 15:09:18 Age [y:d:h:m:s]: 04:278:07:34:36
Block: 64889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091099 RingCT/type: yes/0
Extra: 01931854c7e0942672defd4f63ebf852d26aabb3b4a25473a329dc61a8b7e674b202110ee8583000000000000000000000000000

1 output(s) for total of 374.107674493000 dcy

stealth address amount amount idx
00: 63f41258a84598aa930fb977ce6b6791088142e0d5bc99b6284c4708c3234655 374.107674493000 119755 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": 64899, "vin": [ { "gen": { "height": 64889 } } ], "vout": [ { "amount": 374107674493, "target": { "key": "63f41258a84598aa930fb977ce6b6791088142e0d5bc99b6284c4708c3234655" } } ], "extra": [ 1, 147, 24, 84, 199, 224, 148, 38, 114, 222, 253, 79, 99, 235, 248, 82, 210, 106, 171, 179, 180, 162, 84, 115, 163, 41, 220, 97, 168, 183, 230, 116, 178, 2, 17, 14, 232, 88, 48, 0, 0, 0, 0, 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