Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b2e6645037a6db286e9855406671f4d5e18cc7cdf273ef625f833888b594ac

Tx prefix hash: d38501524592a0dc9e0c7e9ab1ec6cdc0a31789f8a054417225acfc3474c3e45
Tx public key: fee73728b65a2c8df56fab002cd90c353b2cfb46ce2c65e8a12b0ca072e17b7c
Timestamp: 1750601435 Timestamp [UCT]: 2025-06-22 14:10:35 Age [y:d:h:m:s]: 00:150:10:18:48
Block: 1310495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105388 RingCT/type: yes/0
Extra: 01fee73728b65a2c8df56fab002cd90c353b2cfb46ce2c65e8a12b0ca072e17b7c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bdb6415e6e5933c25b01ca00a33352c8925ba51255157c53fa7e84566ce90a4 0.600000000000 1798116 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": 1310505, "vin": [ { "gen": { "height": 1310495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bdb6415e6e5933c25b01ca00a33352c8925ba51255157c53fa7e84566ce90a4" } } ], "extra": [ 1, 254, 231, 55, 40, 182, 90, 44, 141, 245, 111, 171, 0, 44, 217, 12, 53, 59, 44, 251, 70, 206, 44, 101, 232, 161, 43, 12, 160, 114, 225, 123, 124, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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