Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1015d9bad26748c9c9564869ce87103fe90f6069c3c349207edeec52f0f0af17

Tx prefix hash: b3149f52123034149bf46f0f62a76ce3e18c3b8f54f5c416ebef80aa79d3cce6
Tx public key: 4b848c4872b7d0954bcaf0a9b7e89e026374c21c904f19d7b0f0545b12972331
Timestamp: 1711759172 Timestamp [UCT]: 2024-03-30 00:39:32 Age [y:d:h:m:s]: 00:355:06:17:08
Block: 989255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253994 RingCT/type: yes/0
Extra: 014b848c4872b7d0954bcaf0a9b7e89e026374c21c904f19d7b0f0545b129723310211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50d3af2e900895099f05f6bf24280d8038eeb0432d53d2591b5c566510ae89d 0.600000000000 1449550 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": 989265, "vin": [ { "gen": { "height": 989255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50d3af2e900895099f05f6bf24280d8038eeb0432d53d2591b5c566510ae89d" } } ], "extra": [ 1, 75, 132, 140, 72, 114, 183, 208, 149, 75, 202, 240, 169, 183, 232, 158, 2, 99, 116, 194, 28, 144, 79, 25, 215, 176, 240, 84, 91, 18, 151, 35, 49, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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