Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7288bfee554a36d1083304af51f2bff08e7c9fe3deb357b8ce76a8e6bef2d039

Tx prefix hash: 65195dcd09345f251d381a04a085bc6c21ec93bc14221675778ddc49ff94cbe7
Tx public key: d18eefd866d08f1058ecbb4174678fd4ec4f3c8f34478c595737e9ed21a22fe5
Timestamp: 1639428149 Timestamp [UCT]: 2021-12-13 20:42:29 Age [y:d:h:m:s]: 02:346:22:45:30
Block: 394849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766048 RingCT/type: yes/0
Extra: 01d18eefd866d08f1058ecbb4174678fd4ec4f3c8f34478c595737e9ed21a22fe502110000000ae60c8f99000000000000000000

1 output(s) for total of 30.178782310000 dcy

stealth address amount amount idx
00: 7294de6c47c836e9e56fc5c7cd4622a01c2473d03944a57aa0996d6f7be1d62d 30.178782310000 792572 of 0

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": 394859, "vin": [ { "gen": { "height": 394849 } } ], "vout": [ { "amount": 30178782310, "target": { "key": "7294de6c47c836e9e56fc5c7cd4622a01c2473d03944a57aa0996d6f7be1d62d" } } ], "extra": [ 1, 209, 142, 239, 216, 102, 208, 143, 16, 88, 236, 187, 65, 116, 103, 143, 212, 236, 79, 60, 143, 52, 71, 140, 89, 87, 55, 233, 237, 33, 162, 47, 229, 2, 17, 0, 0, 0, 10, 230, 12, 143, 153, 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