Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89614d377d1908621c4b984b96a7da0d5a4f408a58961bf3935b257899876dc4

Tx prefix hash: 749cf492cda8f655fae4d1784989c2859fcec52532d04980c7ceb37a247851e7
Tx public key: 72aa9bdb22594b6560dc9ce9cdae4ea65aa6c8180ad35ca3ebce187a222abb07
Timestamp: 1700473241 Timestamp [UCT]: 2023-11-20 09:40:41 Age [y:d:h:m:s]: 01:095:06:39:25
Block: 895673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329218 RingCT/type: yes/0
Extra: 0172aa9bdb22594b6560dc9ce9cdae4ea65aa6c8180ad35ca3ebce187a222abb07021100000001679a8a81000000000000000000

1 output(s) for total of 0.661094477000 dcy

stealth address amount amount idx
00: db420114bf047ad3c63073e3fa43af6573a6a06d464997abf6c3b1eaf0e8e6e2 0.661094477000 1351914 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": 895683, "vin": [ { "gen": { "height": 895673 } } ], "vout": [ { "amount": 661094477, "target": { "key": "db420114bf047ad3c63073e3fa43af6573a6a06d464997abf6c3b1eaf0e8e6e2" } } ], "extra": [ 1, 114, 170, 155, 219, 34, 89, 75, 101, 96, 220, 156, 233, 205, 174, 78, 166, 90, 166, 200, 24, 10, 211, 92, 163, 235, 206, 24, 122, 34, 42, 187, 7, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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