Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbfc8c0887c620eaa05853c3c9b4e59f0cfab9b205d06462df7b4afc2a71b54d

Tx prefix hash: 638752ff41ec6426089fb70127c7d5eec35dceb4da6090dd8a864105f4b91754
Tx public key: fbf2a8f7459eaf0170116eeb801000759b2fe07c4a77989eee0fd1951c299ae4
Timestamp: 1723618846 Timestamp [UCT]: 2024-08-14 07:00:46 Age [y:d:h:m:s]: 00:237:20:49:42
Block: 1087565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169872 RingCT/type: yes/0
Extra: 01fbf2a8f7459eaf0170116eeb801000759b2fe07c4a77989eee0fd1951c299ae4021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92443aa445827c5a4ec4cf084491926d251b13d68c5cb3e0109c23338bb52f56 0.600000000000 1562174 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": 1087575, "vin": [ { "gen": { "height": 1087565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92443aa445827c5a4ec4cf084491926d251b13d68c5cb3e0109c23338bb52f56" } } ], "extra": [ 1, 251, 242, 168, 247, 69, 158, 175, 1, 112, 17, 110, 235, 128, 16, 0, 117, 155, 47, 224, 124, 74, 119, 152, 158, 238, 15, 209, 149, 28, 41, 154, 228, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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