Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7af6768d93a6b3f30f00d3425fc18508c0b0cfd43d182fff033752107681ab8c

Tx prefix hash: 848f1afe031384665ea5333fe444a6b38dc917fa18fdf42c42b46e08b6359fc7
Tx public key: 764b6d274190fdee5c762460f4c3804cb91358a9000780cc0524a6e9682379b2
Timestamp: 1580480336 Timestamp [UCT]: 2020-01-31 14:18:56 Age [y:d:h:m:s]: 04:280:00:30:26
Block: 55810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091339 RingCT/type: yes/0
Extra: 01764b6d274190fdee5c762460f4c3804cb91358a9000780cc0524a6e9682379b2021100000003dcee4b4d000000000000000000

1 output(s) for total of 400.939760519000 dcy

stealth address amount amount idx
00: da794d1527a86c6bd1c8b05eb2d3f91d3cbbd71c2b26044b284335308d89e51a 400.939760519000 102975 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": 55820, "vin": [ { "gen": { "height": 55810 } } ], "vout": [ { "amount": 400939760519, "target": { "key": "da794d1527a86c6bd1c8b05eb2d3f91d3cbbd71c2b26044b284335308d89e51a" } } ], "extra": [ 1, 118, 75, 109, 39, 65, 144, 253, 238, 92, 118, 36, 96, 244, 195, 128, 76, 185, 19, 88, 169, 0, 7, 128, 204, 5, 36, 166, 233, 104, 35, 121, 178, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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