Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de08eaf0260aea5e804ebeef3bd310dfe4adbb8e7769f9c34546740c5dc5fc20

Tx prefix hash: 6b0bbd8fe0b95cb1a59e0deea335e5de633c9aa41c5867dbe94cae369f565303
Tx public key: 3fd3a1b0eac7062e7a901955736edb47e35902705c9309bb60cb32eded6556f8
Timestamp: 1686030479 Timestamp [UCT]: 2023-06-06 05:47:59 Age [y:d:h:m:s]: 02:011:07:12:57
Block: 776167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530084 RingCT/type: yes/0
Extra: 013fd3a1b0eac7062e7a901955736edb47e35902705c9309bb60cb32eded6556f802110000000175e3f0e9000000000000000000

1 output(s) for total of 1.645268154000 dcy

stealth address amount amount idx
00: b0bbf8e4f136e95c06001bb720626cb2a988e35921b9f45e0e334366aa2526dd 1.645268154000 1225704 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": 776177, "vin": [ { "gen": { "height": 776167 } } ], "vout": [ { "amount": 1645268154, "target": { "key": "b0bbf8e4f136e95c06001bb720626cb2a988e35921b9f45e0e334366aa2526dd" } } ], "extra": [ 1, 63, 211, 161, 176, 234, 199, 6, 46, 122, 144, 25, 85, 115, 110, 219, 71, 227, 89, 2, 112, 92, 147, 9, 187, 96, 203, 50, 237, 237, 101, 86, 248, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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