Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fead585a09a1c3a80a20bfd9f8695972ba49c20722867f2248d5a3f22196b93c

Tx prefix hash: 3cd0f46854c84767b1aca462b002a88b0d4f4f4b6224ef734b2336b4e9786b11
Tx public key: 35576ef3313cc0440fdc9ce93bb8f3d2dabf7980ae0380b3ba1a1ce6455bb8bb
Timestamp: 1708964182 Timestamp [UCT]: 2024-02-26 16:16:22 Age [y:d:h:m:s]: 01:039:18:43:20
Block: 966072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289438 RingCT/type: yes/0
Extra: 0135576ef3313cc0440fdc9ce93bb8f3d2dabf7980ae0380b3ba1a1ce6455bb8bb02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10991ae4e274e9880218a291983af69c39f00a7afe0b3e354c3094a95e77e4dd 0.600000000000 1425829 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": 966082, "vin": [ { "gen": { "height": 966072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10991ae4e274e9880218a291983af69c39f00a7afe0b3e354c3094a95e77e4dd" } } ], "extra": [ 1, 53, 87, 110, 243, 49, 60, 192, 68, 15, 220, 156, 233, 59, 184, 243, 210, 218, 191, 121, 128, 174, 3, 128, 179, 186, 26, 28, 230, 69, 91, 184, 187, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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