Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ed85ab5b4c8641dd490dbf3e090088fb3556709de5743050b99e1823766f76

Tx prefix hash: 42f2e209fabe75e3efdb9f69de88a3da97c1956af447af021946178732e6a9a0
Tx public key: 33c87ec8fbb7eade1e5f8009aa0a6614c90c45540882d03fe027b54fa1e878e0
Timestamp: 1706880863 Timestamp [UCT]: 2024-02-02 13:34:23 Age [y:d:h:m:s]: 01:067:22:22:28
Block: 948783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309616 RingCT/type: yes/0
Extra: 0133c87ec8fbb7eade1e5f8009aa0a6614c90c45540882d03fe027b54fa1e878e002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72cb2f4e80e8f923f4f418280b8a045f6ec8a8de9329870f7fc7dfcd33a2275b 0.600000000000 1407265 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": 948793, "vin": [ { "gen": { "height": 948783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72cb2f4e80e8f923f4f418280b8a045f6ec8a8de9329870f7fc7dfcd33a2275b" } } ], "extra": [ 1, 51, 200, 126, 200, 251, 183, 234, 222, 30, 95, 128, 9, 170, 10, 102, 20, 201, 12, 69, 84, 8, 130, 208, 63, 224, 39, 181, 79, 161, 232, 120, 224, 2, 17, 0, 0, 0, 2, 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