Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fae5d6311dd3f562e5329b29c7b82fb32cddf0f5e26fa7a316bcc2c484048fb

Tx prefix hash: 73276e8a2b6cd8848fd2daa669ccde9551b30db0539c6187821a6dadc6c2d8ae
Tx public key: 9f53725c7bbf490f203f172c46f2024b3782e5f2677b991904443c57ef6ee1e0
Timestamp: 1712479093 Timestamp [UCT]: 2024-04-07 08:38:13 Age [y:d:h:m:s]: 00:315:07:20:47
Block: 995182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225401 RingCT/type: yes/0
Extra: 019f53725c7bbf490f203f172c46f2024b3782e5f2677b991904443c57ef6ee1e00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf210d567e665b8c7ef814fb3dcee3d6eac4f037fcdf50853f83010e77845d2a 0.600000000000 1455588 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": 995192, "vin": [ { "gen": { "height": 995182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf210d567e665b8c7ef814fb3dcee3d6eac4f037fcdf50853f83010e77845d2a" } } ], "extra": [ 1, 159, 83, 114, 92, 123, 191, 73, 15, 32, 63, 23, 44, 70, 242, 2, 75, 55, 130, 229, 242, 103, 123, 153, 25, 4, 68, 60, 87, 239, 110, 225, 224, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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