Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f509c2460d3b0e497cc765c688e2307b26dbb32073f87b0b65bff7c0dc7520de

Tx prefix hash: 81fec2d416b53447aaac9cbb242525217bc4927183a0a58b7a85f8bb8a79ae2e
Tx public key: 40de261e6106f8466d35118d3f7c8522c89f30878d5cdfb781106a201f2626ed
Timestamp: 1716078260 Timestamp [UCT]: 2024-05-19 00:24:20 Age [y:d:h:m:s]: 00:361:11:27:49
Block: 1025043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258391 RingCT/type: yes/0
Extra: 0140de261e6106f8466d35118d3f7c8522c89f30878d5cdfb781106a201f2626ed02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae32856d4e420155841575debc5aae0a3e68e0898f4541348192ab5aae4a1e0e 0.600000000000 1491254 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": 1025053, "vin": [ { "gen": { "height": 1025043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae32856d4e420155841575debc5aae0a3e68e0898f4541348192ab5aae4a1e0e" } } ], "extra": [ 1, 64, 222, 38, 30, 97, 6, 248, 70, 109, 53, 17, 141, 63, 124, 133, 34, 200, 159, 48, 135, 141, 92, 223, 183, 129, 16, 106, 32, 31, 38, 38, 237, 2, 17, 0, 0, 0, 1, 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