Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3db1938d38e0b45631d4f786d110c1a83ae6761de92faf68f322dd8457beae73

Tx prefix hash: 2e2dfb1d4ea84d6caa6f09c0936941a73cc2627a31f35b84fd59c169f991d2ce
Tx public key: 9a4ffd7ebe667ae84839f112a60a6bd907c1e215196b386e95f00c82bd64659b
Timestamp: 1712153011 Timestamp [UCT]: 2024-04-03 14:03:31 Age [y:d:h:m:s]: 00:267:09:11:38
Block: 992472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191423 RingCT/type: yes/0
Extra: 019a4ffd7ebe667ae84839f112a60a6bd907c1e215196b386e95f00c82bd64659b0211000000053f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756b2f1d21d846317f9642bed2c6cdb2e08534315fde1d0dea61179e129331e1 0.600000000000 1452814 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": 992482, "vin": [ { "gen": { "height": 992472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756b2f1d21d846317f9642bed2c6cdb2e08534315fde1d0dea61179e129331e1" } } ], "extra": [ 1, 154, 79, 253, 126, 190, 102, 122, 232, 72, 57, 241, 18, 166, 10, 107, 217, 7, 193, 226, 21, 25, 107, 56, 110, 149, 240, 12, 130, 189, 100, 101, 155, 2, 17, 0, 0, 0, 5, 63, 130, 249, 251, 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