Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c281242d292ebb658e9a69bf6bee4ffbf3de4cde34aa0748c69e8b50341515ca

Tx prefix hash: c1654592e9c72ceb889b85314df17180a68706c63ca5d142c13f805b821d34d5
Tx public key: 8b0d05a8c85c1b5afba47b6aff6b9e3bcfd58e495a291a37272171165b56ce92
Timestamp: 1677931553 Timestamp [UCT]: 2023-03-04 12:05:53 Age [y:d:h:m:s]: 02:072:23:44:54
Block: 709675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573759 RingCT/type: yes/0
Extra: 018b0d05a8c85c1b5afba47b6aff6b9e3bcfd58e495a291a37272171165b56ce920211000000045029cbac000000000000000000

1 output(s) for total of 2.732448743000 dcy

stealth address amount amount idx
00: 4684b761f769b1ad1a4554b9a0a61b54abb62d6a8953217415e39702056d28b2 2.732448743000 1153684 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": 709685, "vin": [ { "gen": { "height": 709675 } } ], "vout": [ { "amount": 2732448743, "target": { "key": "4684b761f769b1ad1a4554b9a0a61b54abb62d6a8953217415e39702056d28b2" } } ], "extra": [ 1, 139, 13, 5, 168, 200, 92, 27, 90, 251, 164, 123, 106, 255, 107, 158, 59, 207, 213, 142, 73, 90, 41, 26, 55, 39, 33, 113, 22, 91, 86, 206, 146, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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