Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19a8e35953d291c741b6acfe1113b2df626d4ad5a32c6e76c5b3ea44643e3804

Tx prefix hash: 1f155833d130798c38078af7ecb2a0031aec532aa43819437b36070cca1f2bc1
Tx public key: 8aeacaf8b59c4b8662bf25c023a5350cf0e57e4118990d390193bb2e93d191f0
Timestamp: 1724325660 Timestamp [UCT]: 2024-08-22 11:21:00 Age [y:d:h:m:s]: 00:266:20:01:31
Block: 1093433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190581 RingCT/type: yes/0
Extra: 018aeacaf8b59c4b8662bf25c023a5350cf0e57e4118990d390193bb2e93d191f002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d52d4fee4350fe01cb0f7208380bb945d526fbd62759fbbfdd41c7816797fff2 0.600000000000 1568374 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": 1093443, "vin": [ { "gen": { "height": 1093433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d52d4fee4350fe01cb0f7208380bb945d526fbd62759fbbfdd41c7816797fff2" } } ], "extra": [ 1, 138, 234, 202, 248, 181, 156, 75, 134, 98, 191, 37, 192, 35, 165, 53, 12, 240, 229, 126, 65, 24, 153, 13, 57, 1, 147, 187, 46, 147, 209, 145, 240, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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