Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beee30e99bdb438847797450fcf9a132dad5461b058089681fe27db19c6a2130

Tx prefix hash: 1f5aae70183fd5bda4822b8b279733458373c2f9d2ac51df0f5b580fa209a20d
Tx public key: 9604aa5f36e4b8b09d32df033e0f59d85afa58456d1bb6d5f84169a8b31a4f86
Timestamp: 1727102131 Timestamp [UCT]: 2024-09-23 14:35:31 Age [y:d:h:m:s]: 00:061:15:19:37
Block: 1116428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44060 RingCT/type: yes/0
Extra: 019604aa5f36e4b8b09d32df033e0f59d85afa58456d1bb6d5f84169a8b31a4f86021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 540f12a53b61e136349c2c903f11619be3643e7bc97029870e2de55ad3605452 0.600000000000 1596907 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": 1116438, "vin": [ { "gen": { "height": 1116428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "540f12a53b61e136349c2c903f11619be3643e7bc97029870e2de55ad3605452" } } ], "extra": [ 1, 150, 4, 170, 95, 54, 228, 184, 176, 157, 50, 223, 3, 62, 15, 89, 216, 90, 250, 88, 69, 109, 27, 182, 213, 248, 65, 105, 168, 179, 26, 79, 134, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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