Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22efa8d8274d1b37986414932f4488af03809e7c5717067e452dc4a6f9b38220

Tx prefix hash: 99ba6c58e4b7af870fc949523025186e680d5ef4d92951eb79baa5d87bc096ac
Tx public key: 3afa6acf9791a8740d3215aae32527f3076ef65b1610a17b8e245262d8c96e72
Timestamp: 1725220565 Timestamp [UCT]: 2024-09-01 19:56:05 Age [y:d:h:m:s]: 00:285:20:58:45
Block: 1100841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204130 RingCT/type: yes/0
Extra: 013afa6acf9791a8740d3215aae32527f3076ef65b1610a17b8e245262d8c96e72021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dff3ca08617cb9639d7f5bb0e1cc8d9b468337012d9be743a6e3279beb281aa4 0.600000000000 1576822 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": 1100851, "vin": [ { "gen": { "height": 1100841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dff3ca08617cb9639d7f5bb0e1cc8d9b468337012d9be743a6e3279beb281aa4" } } ], "extra": [ 1, 58, 250, 106, 207, 151, 145, 168, 116, 13, 50, 21, 170, 227, 37, 39, 243, 7, 110, 246, 91, 22, 16, 161, 123, 142, 36, 82, 98, 216, 201, 110, 114, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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