Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d2641ebc7cdb7f4dcde41a4999477a8277a0a0bed4f253bc2f88fb0dc8aa74

Tx prefix hash: 760b5caa74f1a5fafe37572049f3cf690b5edac326b8cdb3f693eda2edc46fae
Tx public key: 6beb1a5cd6a74758f1cae87e6425c3fcd7ac0f190c66101440cdf413225bed04
Timestamp: 1707029985 Timestamp [UCT]: 2024-02-04 06:59:45 Age [y:d:h:m:s]: 01:063:15:42:54
Block: 950010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306549 RingCT/type: yes/0
Extra: 016beb1a5cd6a74758f1cae87e6425c3fcd7ac0f190c66101440cdf413225bed0402110000000152d47e94000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 56647cacafd9d3be7f7eb895348853814f3034676f8f4e9e79606d37044c6ed0 0.600010000000 1408552 of 0

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": 950020, "vin": [ { "gen": { "height": 950010 } } ], "vout": [ { "amount": 600010000, "target": { "key": "56647cacafd9d3be7f7eb895348853814f3034676f8f4e9e79606d37044c6ed0" } } ], "extra": [ 1, 107, 235, 26, 92, 214, 167, 71, 88, 241, 202, 232, 126, 100, 37, 195, 252, 215, 172, 15, 25, 12, 102, 16, 20, 64, 205, 244, 19, 34, 91, 237, 4, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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