Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398ce663ca60e66fac79a8597be9d134d745e756d777ca2d67ce6a8b29190692

Tx prefix hash: aac1bf7b6771ea440f98a7c4d6755adab0b35dcdc198f1d08b03c69e08eb9467
Tx public key: 805591b1835fc4c9b4fdbef2d993ef11ccb35ade96c2e7ecdbc1e8ab54a53a78
Timestamp: 1712053785 Timestamp [UCT]: 2024-04-02 10:29:45 Age [y:d:h:m:s]: 01:217:15:20:18
Block: 991650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414231 RingCT/type: yes/0
Extra: 01805591b1835fc4c9b4fdbef2d993ef11ccb35ade96c2e7ecdbc1e8ab54a53a780211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ad2f2041dbf547085e54b40584a6b6308ec935d9a0028069863e3b2411d53e 0.600000000000 1451986 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": 991660, "vin": [ { "gen": { "height": 991650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ad2f2041dbf547085e54b40584a6b6308ec935d9a0028069863e3b2411d53e" } } ], "extra": [ 1, 128, 85, 145, 177, 131, 95, 196, 201, 180, 253, 190, 242, 217, 147, 239, 17, 204, 179, 90, 222, 150, 194, 231, 236, 219, 193, 232, 171, 84, 165, 58, 120, 2, 17, 0, 0, 0, 1, 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