Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbd4c0260900c8f7797627fc19ad2be254c79c7e07942f068be02821ccaa688e

Tx prefix hash: e03e3aaaf34a3652617a25fdd77e192a30500760ff97ba0782f819de6606d8fd
Tx public key: f8e819b1dd6fefdb5cb49af797a5d118a01e0629894043163c54473888e4a7bc
Timestamp: 1671996837 Timestamp [UCT]: 2022-12-25 19:33:57 Age [y:d:h:m:s]: 02:080:02:25:47
Block: 660467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 578935 RingCT/type: yes/0
Extra: 01f8e819b1dd6fefdb5cb49af797a5d118a01e0629894043163c54473888e4a7bc021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.977394120000 dcy

stealth address amount amount idx
00: 21fca80caaa439da31c68c0064f3a69ab2fd329151f87eff8cae7f25fd4f99d0 3.977394120000 1101200 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": 660477, "vin": [ { "gen": { "height": 660467 } } ], "vout": [ { "amount": 3977394120, "target": { "key": "21fca80caaa439da31c68c0064f3a69ab2fd329151f87eff8cae7f25fd4f99d0" } } ], "extra": [ 1, 248, 232, 25, 177, 221, 111, 239, 219, 92, 180, 154, 247, 151, 165, 209, 24, 160, 30, 6, 41, 137, 64, 67, 22, 60, 84, 71, 56, 136, 228, 167, 188, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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