Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a40d4397aaae4ae6c0d377580f3c3b6f4ee4ac01580d18a6239e6f4569f37c24

Tx prefix hash: b9b14840f82311101727c12395964c2686fbd923ecfa527a3760e87923173d74
Tx public key: d99c78b10b19842e44d95623bf4d15d6e27b2c484ac9cde94845ed6f434ef0a8
Timestamp: 1734457481 Timestamp [UCT]: 2024-12-17 17:44:41 Age [y:d:h:m:s]: 00:115:19:54:48
Block: 1177330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82548 RingCT/type: yes/0
Extra: 01d99c78b10b19842e44d95623bf4d15d6e27b2c484ac9cde94845ed6f434ef0a8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdba4d1556b26f2ed2285c71be61de9c78d82ec41cc86a24728d317c7e8a0c13 0.600000000000 1663701 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": 1177340, "vin": [ { "gen": { "height": 1177330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdba4d1556b26f2ed2285c71be61de9c78d82ec41cc86a24728d317c7e8a0c13" } } ], "extra": [ 1, 217, 156, 120, 177, 11, 25, 132, 46, 68, 217, 86, 35, 191, 77, 21, 214, 226, 123, 44, 72, 74, 201, 205, 233, 72, 69, 237, 111, 67, 78, 240, 168, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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