Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b0a6dc6df678171daf143d2ff35e395c3a5966159c106361cc40b74a772a7c8

Tx prefix hash: c9b9880366c9727bb0320a2f840a7c52f9ab0828587fe3549003f33d0c0076cb
Tx public key: 7b4abd33493523a7d32ae7f4792a696eeddd08043c23f6447cd6cf6709c309be
Timestamp: 1708911147 Timestamp [UCT]: 2024-02-26 01:32:27 Age [y:d:h:m:s]: 01:111:02:41:14
Block: 965631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340366 RingCT/type: yes/0
Extra: 017b4abd33493523a7d32ae7f4792a696eeddd08043c23f6447cd6cf6709c309be02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb5f0f1c796256dc037c9fa322d009873ef2e8a42914785dfeb2ef06ef44e6ac 0.600000000000 1425384 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": 965641, "vin": [ { "gen": { "height": 965631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb5f0f1c796256dc037c9fa322d009873ef2e8a42914785dfeb2ef06ef44e6ac" } } ], "extra": [ 1, 123, 74, 189, 51, 73, 53, 35, 167, 211, 42, 231, 244, 121, 42, 105, 110, 237, 221, 8, 4, 60, 35, 246, 68, 124, 214, 207, 103, 9, 195, 9, 190, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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