Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1feb8a1629ef4589155480e3600a42764f822afe4a1d27e5a46d3559c8e88f

Tx prefix hash: b4a5784cced5c7d011fbf0c714c10fe9f5a100cbfa1f6d98df6b6d5febe27f93
Tx public key: ff99b6a32a333356089dba81610c659d63ed10ebeef496643509f160f978e775
Timestamp: 1696279921 Timestamp [UCT]: 2023-10-02 20:52:01 Age [y:d:h:m:s]: 01:187:02:39:33
Block: 861111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394757 RingCT/type: yes/0
Extra: 01ff99b6a32a333356089dba81610c659d63ed10ebeef496643509f160f978e775021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.860561343000 dcy

stealth address amount amount idx
00: d0d6e83a0ce8946332314479ad96149473c8b2e3a5a3dbe7993074530c13d3a7 0.860561343000 1315427 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": 861121, "vin": [ { "gen": { "height": 861111 } } ], "vout": [ { "amount": 860561343, "target": { "key": "d0d6e83a0ce8946332314479ad96149473c8b2e3a5a3dbe7993074530c13d3a7" } } ], "extra": [ 1, 255, 153, 182, 163, 42, 51, 51, 86, 8, 157, 186, 129, 97, 12, 101, 157, 99, 237, 16, 235, 238, 244, 150, 100, 53, 9, 241, 96, 249, 120, 231, 117, 2, 17, 0, 0, 0, 6, 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