Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652f7f3eab5cca031d481cf339303ed64195d1df974bf6e5faf2d9448ef48a1f

Tx prefix hash: 0aadaff7ac4ac696417ba12b267e814b0a29b10fc3650ae408bf57d71cbf078f
Tx public key: 0ba2dd38cf6c42576b348d743e231520502b4dc21baa5b16a939fc4183c24f10
Timestamp: 1745840386 Timestamp [UCT]: 2025-04-28 11:39:46 Age [y:d:h:m:s]: 00:013:00:40:51
Block: 1271274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9314 RingCT/type: yes/0
Extra: 010ba2dd38cf6c42576b348d743e231520502b4dc21baa5b16a939fc4183c24f100211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1bc0e0b8cf3b3f805802042f606fc2197b10f629e2cc7b964feddf1363eb8dd 0.600000000000 1758531 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": 1271284, "vin": [ { "gen": { "height": 1271274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1bc0e0b8cf3b3f805802042f606fc2197b10f629e2cc7b964feddf1363eb8dd" } } ], "extra": [ 1, 11, 162, 221, 56, 207, 108, 66, 87, 107, 52, 141, 116, 62, 35, 21, 32, 80, 43, 77, 194, 27, 170, 91, 22, 169, 57, 252, 65, 131, 194, 79, 16, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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