Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd8ff81f43077bb58d67f02e5a184b4e05271cb843eb311d030373cc7b8eecf

Tx prefix hash: 834679b182c9164e342d12dbc92e473a7b46675af3ce83620cb1378db463cfc3
Tx public key: b74b2bdc0904367b68833a4d2f3185c3a7bdc42a7b06c665788767ffb441043c
Timestamp: 1714336497 Timestamp [UCT]: 2024-04-28 20:34:57 Age [y:d:h:m:s]: 00:256:08:30:16
Block: 1010597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183492 RingCT/type: yes/0
Extra: 01b74b2bdc0904367b68833a4d2f3185c3a7bdc42a7b06c665788767ffb441043c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d210fda25d9c43236b8e2fa35ed2c877d9c03d89be24e3c28224d9c70539da8c 0.600000000000 1472599 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": 1010607, "vin": [ { "gen": { "height": 1010597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d210fda25d9c43236b8e2fa35ed2c877d9c03d89be24e3c28224d9c70539da8c" } } ], "extra": [ 1, 183, 75, 43, 220, 9, 4, 54, 123, 104, 131, 58, 77, 47, 49, 133, 195, 167, 189, 196, 42, 123, 6, 198, 101, 120, 135, 103, 255, 180, 65, 4, 60, 2, 17, 0, 0, 0, 3, 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