Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30516835f1a1f3bd90dd1a1343b40294a10b1670b883c0376a7aab57fc79f5a6

Tx prefix hash: 3aaf786966bfca010b39eae1d140aec06ae2cf14a3e2db90d733876897bc52d5
Tx public key: a84d9745c85cd7e0a8f45934ab8d38436f60aa33fa8e58cb50e599b11435f406
Timestamp: 1729833646 Timestamp [UCT]: 2024-10-25 05:20:46 Age [y:d:h:m:s]: 00:030:08:42:26
Block: 1139046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21691 RingCT/type: yes/0
Extra: 01a84d9745c85cd7e0a8f45934ab8d38436f60aa33fa8e58cb50e599b11435f4060211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499dca05e96a6c4db4999784b2e1e13e303fd10ab3fc9fa2d6efbf567b9c7511 0.600000000000 1622801 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": 1139056, "vin": [ { "gen": { "height": 1139046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499dca05e96a6c4db4999784b2e1e13e303fd10ab3fc9fa2d6efbf567b9c7511" } } ], "extra": [ 1, 168, 77, 151, 69, 200, 92, 215, 224, 168, 244, 89, 52, 171, 141, 56, 67, 111, 96, 170, 51, 250, 142, 88, 203, 80, 229, 153, 177, 20, 53, 244, 6, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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