Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 586f24c6eafb708a69e23890d57c41a79d7aa7e12aaec7ba0b229c62462c6955

Tx prefix hash: 27a4c854ec4734ead73c97618508565819936b1170aeb02a6d11cbd1030cdb57
Tx public key: 2bc0b2c2efd2843c6835d5d2a5b6be83fa268636557f16da284b1b562bd13e56
Timestamp: 1734355558 Timestamp [UCT]: 2024-12-16 13:25:58 Age [y:d:h:m:s]: 00:185:09:53:35
Block: 1176486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132184 RingCT/type: yes/0
Extra: 012bc0b2c2efd2843c6835d5d2a5b6be83fa268636557f16da284b1b562bd13e560211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a32c049d492d7c3ac1669bcf35739d31d369ba0b431a79b0818857284bcc6e9 0.600000000000 1662819 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": 1176496, "vin": [ { "gen": { "height": 1176486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a32c049d492d7c3ac1669bcf35739d31d369ba0b431a79b0818857284bcc6e9" } } ], "extra": [ 1, 43, 192, 178, 194, 239, 210, 132, 60, 104, 53, 213, 210, 165, 182, 190, 131, 250, 38, 134, 54, 85, 127, 22, 218, 40, 75, 27, 86, 43, 209, 62, 86, 2, 17, 0, 0, 0, 9, 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