Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0738438b92850f53c27d9b35553850b0d0fa10d62e3f2049140239afcf17e74a

Tx prefix hash: 3b14cc980199492fdded6e702e079fffa1a339d600f4ee0bdb5c85fab0d47147
Tx public key: 6ad3eeead8a5343b5ce324a8bd118c4da1bd15d3df840c34a603a1b708126a8c
Timestamp: 1574220806 Timestamp [UCT]: 2019-11-20 03:33:26 Age [y:d:h:m:s]: 05:082:12:22:10
Block: 12949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1201944 RingCT/type: yes/0
Extra: 016ad3eeead8a5343b5ce324a8bd118c4da1bd15d3df840c34a603a1b708126a8c021100000003ccefb800000000000000000000

1 output(s) for total of 556.026480026000 dcy

stealth address amount amount idx
00: b81d007d244106c12736c03b6d2da62ad33eeb22799038417b4786ecf5e759b2 556.026480026000 14863 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": 12959, "vin": [ { "gen": { "height": 12949 } } ], "vout": [ { "amount": 556026480026, "target": { "key": "b81d007d244106c12736c03b6d2da62ad33eeb22799038417b4786ecf5e759b2" } } ], "extra": [ 1, 106, 211, 238, 234, 216, 165, 52, 59, 92, 227, 36, 168, 189, 17, 140, 77, 161, 189, 21, 211, 223, 132, 12, 52, 166, 3, 161, 183, 8, 18, 106, 140, 2, 17, 0, 0, 0, 3, 204, 239, 184, 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