Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b81e440734b7024ede789ad641301adb6be6cbe8c560639c3dc6c5902e55a1

Tx prefix hash: be58adcffbda8412e4941f74aa748c4603cc15367fcc8671ea5695f1a4c39a8a
Tx public key: 33041848ce48e8b21b7d288ebb8cbe835a04a4d32f0f2fe47d18ff2dd7bb843c
Timestamp: 1737001637 Timestamp [UCT]: 2025-01-16 04:27:17 Age [y:d:h:m:s]: 00:154:03:59:53
Block: 1198358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109873 RingCT/type: yes/0
Extra: 0133041848ce48e8b21b7d288ebb8cbe835a04a4d32f0f2fe47d18ff2dd7bb843c02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae08b7501702f6eec87c5a0c24b386df8a0d638b30c8372f201a1d122c797a3 0.600000000000 1684981 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": 1198368, "vin": [ { "gen": { "height": 1198358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae08b7501702f6eec87c5a0c24b386df8a0d638b30c8372f201a1d122c797a3" } } ], "extra": [ 1, 51, 4, 24, 72, 206, 72, 232, 178, 27, 125, 40, 142, 187, 140, 190, 131, 90, 4, 164, 211, 47, 15, 47, 228, 125, 24, 255, 45, 215, 187, 132, 60, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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