Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29ad0d63255454f2901ad35ae60d860dd5bf4455a161f6935703a3137a467b68

Tx prefix hash: 08815ab77937e3db345d844343c935e4eeca808b8d91601acd2f594d8de94fc0
Tx public key: 14de234bddba6f3e6f5f9a91a120b5002edfb283b990ce0d42c7e45953a238af
Timestamp: 1581823511 Timestamp [UCT]: 2020-02-16 03:25:11 Age [y:d:h:m:s]: 04:321:11:57:03
Block: 65914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122047 RingCT/type: yes/0
Extra: 0114de234bddba6f3e6f5f9a91a120b5002edfb283b990ce0d42c7e45953a238af021100000003c71d3ff9000000000000000000

1 output(s) for total of 371.193502407000 dcy

stealth address amount amount idx
00: 910cbc7c0106334ae2295e5882982f0cab90d12dd76f899dafef39c8cc0f8d7d 371.193502407000 121537 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": 65924, "vin": [ { "gen": { "height": 65914 } } ], "vout": [ { "amount": 371193502407, "target": { "key": "910cbc7c0106334ae2295e5882982f0cab90d12dd76f899dafef39c8cc0f8d7d" } } ], "extra": [ 1, 20, 222, 35, 75, 221, 186, 111, 62, 111, 95, 154, 145, 161, 32, 181, 0, 46, 223, 178, 131, 185, 144, 206, 13, 66, 199, 228, 89, 83, 162, 56, 175, 2, 17, 0, 0, 0, 3, 199, 29, 63, 249, 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