Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86296dc8fc57dddedfd3fe99acc33cca477c6c779ea859e2fffe067a081e504a

Tx prefix hash: 2cd55230a964cdd1c234d1cbcd2257d74e245d0ee7fa11e92b6fca6eb1efaa19
Tx public key: 3f64432452405a1ec8e4dbad6466c39455dce945cb7d272107568b84c60659b6
Timestamp: 1702089781 Timestamp [UCT]: 2023-12-09 02:43:01 Age [y:d:h:m:s]: 00:342:01:00:15
Block: 909064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244913 RingCT/type: yes/0
Extra: 013f64432452405a1ec8e4dbad6466c39455dce945cb7d272107568b84c60659b602110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af11b25e593c6e6ec6d5d3e7f25d0440978b0acde3d43f9c677744c7bdbbbb07 0.600000000000 1366129 of 15

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": 909074, "vin": [ { "gen": { "height": 909064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af11b25e593c6e6ec6d5d3e7f25d0440978b0acde3d43f9c677744c7bdbbbb07" } } ], "extra": [ 1, 63, 100, 67, 36, 82, 64, 90, 30, 200, 228, 219, 173, 100, 102, 195, 148, 85, 220, 233, 69, 203, 125, 39, 33, 7, 86, 139, 132, 198, 6, 89, 182, 2, 17, 0, 0, 0, 11, 250, 243, 92, 156, 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