Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d58e1a974d5954c6663bc2ba72d33b99c9f5c6ddc3f4a6d129293cf7d3cadfb

Tx prefix hash: b121f37a9fc8f7b6aada4eadd093a767d9620c7800ee734793af73a05fc18b81
Tx public key: bda15270e2d8a3b241774775b906e7c56e916bbf381ea5ef902b441131ad67d0
Timestamp: 1588517294 Timestamp [UCT]: 2020-05-03 14:48:14 Age [y:d:h:m:s]: 04:243:19:49:42
Block: 98378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089435 RingCT/type: yes/0
Extra: 01bda15270e2d8a3b241774775b906e7c56e916bbf381ea5ef902b441131ad67d00211000000044ac5aa02000000000000000000

1 output(s) for total of 289.756783236000 dcy

stealth address amount amount idx
00: dfbc7b2fd044aab1ae0b7ea1c50e21202a4fa9cbffedea6c35c6b115e4519848 289.756783236000 173815 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": 98388, "vin": [ { "gen": { "height": 98378 } } ], "vout": [ { "amount": 289756783236, "target": { "key": "dfbc7b2fd044aab1ae0b7ea1c50e21202a4fa9cbffedea6c35c6b115e4519848" } } ], "extra": [ 1, 189, 161, 82, 112, 226, 216, 163, 178, 65, 119, 71, 117, 185, 6, 231, 197, 110, 145, 107, 191, 56, 30, 165, 239, 144, 43, 68, 17, 49, 173, 103, 208, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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