Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b02552f3b238f0678c34e119846bb8521f40b4b09981835ea51ef2793b766d2

Tx prefix hash: 7e688dcb46992de1d4116f23eb9c5899c183e5e735661f87d8e5854f0dd15cb0
Tx public key: 69bc82c0e5026d1d9241f60f04974983927782c91c671d225f3e536ce9d7b938
Timestamp: 1737064515 Timestamp [UCT]: 2025-01-16 21:55:15 Age [y:d:h:m:s]: 00:155:20:29:40
Block: 1198870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111056 RingCT/type: yes/0
Extra: 0169bc82c0e5026d1d9241f60f04974983927782c91c671d225f3e536ce9d7b9380211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba966b06597a7a52e800857b051aad4dc7fcb8d2c58f5f0fd9905ee6685f11c9 0.600000000000 1685497 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": 1198880, "vin": [ { "gen": { "height": 1198870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba966b06597a7a52e800857b051aad4dc7fcb8d2c58f5f0fd9905ee6685f11c9" } } ], "extra": [ 1, 105, 188, 130, 192, 229, 2, 109, 29, 146, 65, 246, 15, 4, 151, 73, 131, 146, 119, 130, 201, 28, 103, 29, 34, 95, 62, 83, 108, 233, 215, 185, 56, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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