Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1489d29ac32345d315dd12972c2961a32170435da6fd1af3e775e3abedc7fd2

Tx prefix hash: 8572ca5ace90a66b3abe0225fb5f94fc1b018c0ff37576e296eaf12e496c43a7
Tx public key: 808e994458bc0f2177f3344b7aeba21d1b20c0c245ace7a8610102e5743b0876
Timestamp: 1649576471 Timestamp [UCT]: 2022-04-10 07:41:11 Age [y:d:h:m:s]: 02:347:00:42:18
Block: 477133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 767573 RingCT/type: yes/0
Extra: 01808e994458bc0f2177f3344b7aeba21d1b20c0c245ace7a8610102e5743b08760211000000152e6b1fd5000000000000000000

1 output(s) for total of 16.108701824000 dcy

stealth address amount amount idx
00: ee3c298e289a85e1f664223b6f402dc3bd8b018fbb051364367f5d2ae8c96b57 16.108701824000 897760 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": 477143, "vin": [ { "gen": { "height": 477133 } } ], "vout": [ { "amount": 16108701824, "target": { "key": "ee3c298e289a85e1f664223b6f402dc3bd8b018fbb051364367f5d2ae8c96b57" } } ], "extra": [ 1, 128, 142, 153, 68, 88, 188, 15, 33, 119, 243, 52, 75, 122, 235, 162, 29, 27, 32, 192, 194, 69, 172, 231, 168, 97, 1, 2, 229, 116, 59, 8, 118, 2, 17, 0, 0, 0, 21, 46, 107, 31, 213, 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