Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f140ee7c74a5cf79f0457cbd4dd14d35f37f4f2189274725ead29f0c836a434

Tx prefix hash: 56dc04d84ed5dbf67f22b92acb58c3bcf2e0d6fb77a8b128b2deb7376cb5f884
Tx public key: 0e594f42aef5bea4c76c9836036102de41ae64cb38d19c91bb9a82f355517c77
Timestamp: 1582977171 Timestamp [UCT]: 2020-02-29 11:52:51 Age [y:d:h:m:s]: 05:061:18:04:55
Block: 74045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198491 RingCT/type: yes/0
Extra: 010e594f42aef5bea4c76c9836036102de41ae64cb38d19c91bb9a82f355517c770211000000c67adf42d3000000000000000000

1 output(s) for total of 348.866265378000 dcy

stealth address amount amount idx
00: 8d1c9644a2dc1e03dc93b6b6c5fcd4c9097a33b89f93dbbb99596824cae5e414 348.866265378000 136845 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": 74055, "vin": [ { "gen": { "height": 74045 } } ], "vout": [ { "amount": 348866265378, "target": { "key": "8d1c9644a2dc1e03dc93b6b6c5fcd4c9097a33b89f93dbbb99596824cae5e414" } } ], "extra": [ 1, 14, 89, 79, 66, 174, 245, 190, 164, 199, 108, 152, 54, 3, 97, 2, 222, 65, 174, 100, 203, 56, 209, 156, 145, 187, 154, 130, 243, 85, 81, 124, 119, 2, 17, 0, 0, 0, 198, 122, 223, 66, 211, 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