Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 269f0befe01c0ba3b65880937b543a0c7e5a1fe3256a9585035f3fa842a0fdb0

Tx prefix hash: bf84faf95f4f3b523397e81677e98137e0c439443bee48d11fef8deb74875d5b
Tx public key: 8b2962f0376eda9d495e52536f833898832261edffc7e08cb24331ea545ed6e1
Timestamp: 1726608616 Timestamp [UCT]: 2024-09-17 21:30:16 Age [y:d:h:m:s]: 00:207:14:59:05
Block: 1112341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148224 RingCT/type: yes/0
Extra: 018b2962f0376eda9d495e52536f833898832261edffc7e08cb24331ea545ed6e102110000002891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65929007c365f850b9f38c7e4e29653c608999f1f873a0cc8b88db9c7e7d783b 0.600000000000 1591628 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": 1112351, "vin": [ { "gen": { "height": 1112341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65929007c365f850b9f38c7e4e29653c608999f1f873a0cc8b88db9c7e7d783b" } } ], "extra": [ 1, 139, 41, 98, 240, 55, 110, 218, 157, 73, 94, 82, 83, 111, 131, 56, 152, 131, 34, 97, 237, 255, 199, 224, 140, 178, 67, 49, 234, 84, 94, 214, 225, 2, 17, 0, 0, 0, 40, 145, 225, 60, 4, 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