Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fab5b9b5279dcef71e9ada489475473876f495d8063ebf96d5c754e2ec92e56

Tx prefix hash: ba2839e1136224e660e96276ef437be4d398199fb397c63162859e53f68bbddf
Tx public key: 5f0aa6478a9f6b2712c2cf14912a1afc2fa3084df00f15e73d9322612b8738b8
Timestamp: 1713977914 Timestamp [UCT]: 2024-04-24 16:58:34 Age [y:d:h:m:s]: 01:008:15:33:59
Block: 1007630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267127 RingCT/type: yes/0
Extra: 015f0aa6478a9f6b2712c2cf14912a1afc2fa3084df00f15e73d9322612b8738b80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 442517c5f6cf616ccc92936d6c5e589fbe4a53453697d688becf2af87249a4a4 0.600000000000 1469036 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": 1007640, "vin": [ { "gen": { "height": 1007630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "442517c5f6cf616ccc92936d6c5e589fbe4a53453697d688becf2af87249a4a4" } } ], "extra": [ 1, 95, 10, 166, 71, 138, 159, 107, 39, 18, 194, 207, 20, 145, 42, 26, 252, 47, 163, 8, 77, 240, 15, 21, 231, 61, 147, 34, 97, 43, 135, 56, 184, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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