Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9692be6d958455582ad80c3bc437e51d5c4b5130ea5bbccadb2adb45aa6778a0

Tx prefix hash: 9940c3b07db91e0389ef0dc128470ff1111743ed942e3d8b71486e84629cb7a8
Tx public key: 638ef7e07e4ecf75e97ee14252bd78e62d4e4709742f3b9d6d11f357844fa4b1
Timestamp: 1578000561 Timestamp [UCT]: 2020-01-02 21:29:21 Age [y:d:h:m:s]: 05:006:16:18:51
Block: 37434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154773 RingCT/type: yes/0
Extra: 01638ef7e07e4ecf75e97ee14252bd78e62d4e4709742f3b9d6d11f357844fa4b1021100000005d81c26c0000000000000000000

1 output(s) for total of 461.281959387000 dcy

stealth address amount amount idx
00: f18efb49878685b7e1662b4786657812f5f6efd8aa1d45f365511f222b593d2e 461.281959387000 63544 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": 37444, "vin": [ { "gen": { "height": 37434 } } ], "vout": [ { "amount": 461281959387, "target": { "key": "f18efb49878685b7e1662b4786657812f5f6efd8aa1d45f365511f222b593d2e" } } ], "extra": [ 1, 99, 142, 247, 224, 126, 78, 207, 117, 233, 126, 225, 66, 82, 189, 120, 230, 45, 78, 71, 9, 116, 47, 59, 157, 109, 17, 243, 87, 132, 79, 164, 177, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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