Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2fd75f4dd280c6a7360a4174497dbfdb6813f8fcefceaac06bb26c1582379a

Tx prefix hash: 05a4db5d3299ea211db75c319bd8369edc22ea01684620ee679a37b3cc82ae7e
Tx public key: 5bf6a38329a292b32b360e1ac07d75f3b8fc6d92fd3d66f6a438a2cfb97ce937
Timestamp: 1707445057 Timestamp [UCT]: 2024-02-09 02:17:37 Age [y:d:h:m:s]: 01:015:20:20:42
Block: 953461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272343 RingCT/type: yes/0
Extra: 015bf6a38329a292b32b360e1ac07d75f3b8fc6d92fd3d66f6a438a2cfb97ce93702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 669d9932f8ac6e04d874991cee63f6974ade164dcf8cd7a486a9e6b49488879c 0.600000000000 1412673 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": 953471, "vin": [ { "gen": { "height": 953461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "669d9932f8ac6e04d874991cee63f6974ade164dcf8cd7a486a9e6b49488879c" } } ], "extra": [ 1, 91, 246, 163, 131, 41, 162, 146, 179, 43, 54, 14, 26, 192, 125, 117, 243, 184, 252, 109, 146, 253, 61, 102, 246, 164, 56, 162, 207, 185, 124, 233, 55, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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