Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef0b8b875ad83dbbbcc16a7cfc15abbc70b6cf92a4948bb2161cefa66f0d655

Tx prefix hash: 923dcd51d0e341e1580cdb3b167a7462d4c95bfe01ae9db64f73d1dee2fa3b40
Tx public key: b96807a74eb4ad7afc7ccd11bdaf12a20df887bfd65da09b0179d680c520af90
Timestamp: 1581257027 Timestamp [UCT]: 2020-02-09 14:03:47 Age [y:d:h:m:s]: 05:096:06:17:14
Block: 61448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221531 RingCT/type: yes/0
Extra: 01b96807a74eb4ad7afc7ccd11bdaf12a20df887bfd65da09b0179d680c520af9002110000000ad81c26c0000000000000000000

1 output(s) for total of 384.073801287000 dcy

stealth address amount amount idx
00: e708b2abda0d0d38725a1330a45f11b065db1217252b8e9bfad80165f194bc03 384.073801287000 113244 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": 61458, "vin": [ { "gen": { "height": 61448 } } ], "vout": [ { "amount": 384073801287, "target": { "key": "e708b2abda0d0d38725a1330a45f11b065db1217252b8e9bfad80165f194bc03" } } ], "extra": [ 1, 185, 104, 7, 167, 78, 180, 173, 122, 252, 124, 205, 17, 189, 175, 18, 162, 13, 248, 135, 191, 214, 93, 160, 155, 1, 121, 214, 128, 197, 32, 175, 144, 2, 17, 0, 0, 0, 10, 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