Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c049722775ce596882bd6e985bfa005a9cb79217552369eb27813958072f85f

Tx prefix hash: 5835f23a73fb285c1a65fd3c18d08a4708b2b1c88e395d5cac880afb9d177354
Tx public key: 1da6871fdd08d2face41d91227b60144cd6e51811e10d9d07d99e1051cfae8ef
Timestamp: 1699373749 Timestamp [UCT]: 2023-11-07 16:15:49 Age [y:d:h:m:s]: 01:147:16:47:49
Block: 886557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366744 RingCT/type: yes/0
Extra: 011da6871fdd08d2face41d91227b60144cd6e51811e10d9d07d99e1051cfae8ef0211000000164b8f5122000000000000000000

1 output(s) for total of 0.708710121000 dcy

stealth address amount amount idx
00: 42cc19a9083559a01877ffe2c5f6d0623d51de5e62495b4f16cd49695b0c7f6f 0.708710121000 1342384 of 0

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": 886567, "vin": [ { "gen": { "height": 886557 } } ], "vout": [ { "amount": 708710121, "target": { "key": "42cc19a9083559a01877ffe2c5f6d0623d51de5e62495b4f16cd49695b0c7f6f" } } ], "extra": [ 1, 29, 166, 135, 31, 221, 8, 210, 250, 206, 65, 217, 18, 39, 182, 1, 68, 205, 110, 81, 129, 30, 16, 217, 208, 125, 153, 225, 5, 28, 250, 232, 239, 2, 17, 0, 0, 0, 22, 75, 143, 81, 34, 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