Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa5cce3556526be6b52b834f428b69789464271b27a6a09f33b9b2d6a2c494ae

Tx prefix hash: 9d3fed336e477a26144d6400c1618deb1576f84e7c5403648c005b7d48cea2e9
Tx public key: c76283b8fd45a7ae0da4ffdab01a6301f2a3e1806887201caacf31125801f723
Timestamp: 1706922786 Timestamp [UCT]: 2024-02-03 01:13:06 Age [y:d:h:m:s]: 00:347:21:18:36
Block: 949127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249050 RingCT/type: yes/0
Extra: 01c76283b8fd45a7ae0da4ffdab01a6301f2a3e1806887201caacf31125801f7230211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81e9d41e58de91c2e58327a69c6d2b40e8869e5ce14e35396c751bc8ea063c5f 0.600000000000 1407649 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": 949137, "vin": [ { "gen": { "height": 949127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81e9d41e58de91c2e58327a69c6d2b40e8869e5ce14e35396c751bc8ea063c5f" } } ], "extra": [ 1, 199, 98, 131, 184, 253, 69, 167, 174, 13, 164, 255, 218, 176, 26, 99, 1, 242, 163, 225, 128, 104, 135, 32, 28, 170, 207, 49, 18, 88, 1, 247, 35, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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