Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 052e06481775d1c66bc719e61ca22062a963c157dd938c62e011ea5a372f5ffa

Tx prefix hash: 59a8ae1b5efab3eb08defa5c1e7a0d405f8f25c3e3d4a690178e2b1afdf78a86
Tx public key: 8ba5bdd8ec7ea2d68ee652e260cbfbb909125e044b11ae19f030c2a1ce810025
Timestamp: 1719757618 Timestamp [UCT]: 2024-06-30 14:26:58 Age [y:d:h:m:s]: 00:263:03:20:22
Block: 1055535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188042 RingCT/type: yes/0
Extra: 018ba5bdd8ec7ea2d68ee652e260cbfbb909125e044b11ae19f030c2a1ce81002502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32af4859987ccfc2ec8466afa409d49e4c6d386312d8febf784528c8edb2b2d1 0.600000000000 1525940 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": 1055545, "vin": [ { "gen": { "height": 1055535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32af4859987ccfc2ec8466afa409d49e4c6d386312d8febf784528c8edb2b2d1" } } ], "extra": [ 1, 139, 165, 189, 216, 236, 126, 162, 214, 142, 230, 82, 226, 96, 203, 251, 185, 9, 18, 94, 4, 75, 17, 174, 25, 240, 48, 194, 161, 206, 129, 0, 37, 2, 17, 0, 0, 0, 3, 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