Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdebafe34a799a262ebce3dc4df7b0a11d8ff406f3efd590a1240b2b7afb8d47

Tx prefix hash: ee6fd55c238736c7ef06ed2607a3a4ca480dbeef0f107da5ec812e0b0d21929b
Tx public key: f925df172361d5024de61462ec3636de9f34129080a022743a7bea87ec84b49f
Timestamp: 1698575718 Timestamp [UCT]: 2023-10-29 10:35:18 Age [y:d:h:m:s]: 01:142:07:26:28
Block: 880152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362713 RingCT/type: yes/0
Extra: 01f925df172361d5024de61462ec3636de9f34129080a022743a7bea87ec84b49f02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.744202403000 dcy

stealth address amount amount idx
00: 0dab2e1841e53146862ec6ffc80b8178dcf34edbab3c1387af51d9fc8885a817 0.744202403000 1335698 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": 880162, "vin": [ { "gen": { "height": 880152 } } ], "vout": [ { "amount": 744202403, "target": { "key": "0dab2e1841e53146862ec6ffc80b8178dcf34edbab3c1387af51d9fc8885a817" } } ], "extra": [ 1, 249, 37, 223, 23, 35, 97, 213, 2, 77, 230, 20, 98, 236, 54, 54, 222, 159, 52, 18, 144, 128, 160, 34, 116, 58, 123, 234, 135, 236, 132, 180, 159, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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