Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7de425e723dfc97e42157b18a0bf262ff3df5f1268041abb3630a87abcbd1b7

Tx prefix hash: 72dd50b917f4f0d7aa959fde95d2549276604e23b5deedc481c8c4f5c3032b27
Tx public key: e45a7142ee07ef8919381e3a723a9052b83936e3caca30c834a4a14ac0c9b0e8
Timestamp: 1709898540 Timestamp [UCT]: 2024-03-08 11:49:00 Age [y:d:h:m:s]: 01:059:06:59:20
Block: 973826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303379 RingCT/type: yes/0
Extra: 01e45a7142ee07ef8919381e3a723a9052b83936e3caca30c834a4a14ac0c9b0e802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 759677d33467b1c34981e33b1341560f5bd7460e6f1fe414e101526c1498b56e 0.600000000000 1433767 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": 973836, "vin": [ { "gen": { "height": 973826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "759677d33467b1c34981e33b1341560f5bd7460e6f1fe414e101526c1498b56e" } } ], "extra": [ 1, 228, 90, 113, 66, 238, 7, 239, 137, 25, 56, 30, 58, 114, 58, 144, 82, 184, 57, 54, 227, 202, 202, 48, 200, 52, 164, 161, 74, 192, 201, 176, 232, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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