Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055d0bb131849514a008e66e8be157faab7cda9990205d9a29f184888a04fc91

Tx prefix hash: c1a912a3ed33081c0014f4a655b17cc475dd0581d4f6c4d2f8fca983f4d9272c
Tx public key: e776563d4bed82cc35dc2a591db50d59348c5e7ce98348013e23c0aa3f338280
Timestamp: 1709215929 Timestamp [UCT]: 2024-02-29 14:12:09 Age [y:d:h:m:s]: 00:269:04:30:58
Block: 968155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192716 RingCT/type: yes/0
Extra: 01e776563d4bed82cc35dc2a591db50d59348c5e7ce98348013e23c0aa3f33828002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d16ae44ed35bdcbd8768a1a424c8bcb8e41a133934dea57525338faf0b5061b3 0.600000000000 1427954 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": 968165, "vin": [ { "gen": { "height": 968155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d16ae44ed35bdcbd8768a1a424c8bcb8e41a133934dea57525338faf0b5061b3" } } ], "extra": [ 1, 231, 118, 86, 61, 75, 237, 130, 204, 53, 220, 42, 89, 29, 181, 13, 89, 52, 140, 94, 124, 233, 131, 72, 1, 62, 35, 192, 170, 63, 51, 130, 128, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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