Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde7ec522103ad028195e9875e64a8c9ef07f912fdbc46c82c5ccf2ee2fcacfc

Tx prefix hash: 530d89d2c58d668a31b0c2dc34b3b4c844437dae43a77d83587befb9b914ca0c
Tx public key: fa6ea3ac345a362498f314d450612ae6cea60f387f86edbaeeb8a64ac4bd14ac
Timestamp: 1726019012 Timestamp [UCT]: 2024-09-11 01:43:32 Age [y:d:h:m:s]: 01:056:03:00:08
Block: 1107459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298506 RingCT/type: yes/0
Extra: 01fa6ea3ac345a362498f314d450612ae6cea60f387f86edbaeeb8a64ac4bd14ac021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf37120aa837f6dc2a9da3fe9f31b352e3674aa16c194811bbd6f87cf79ad6bf 0.600000000000 1585072 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": 1107469, "vin": [ { "gen": { "height": 1107459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf37120aa837f6dc2a9da3fe9f31b352e3674aa16c194811bbd6f87cf79ad6bf" } } ], "extra": [ 1, 250, 110, 163, 172, 52, 90, 54, 36, 152, 243, 20, 212, 80, 97, 42, 230, 206, 166, 15, 56, 127, 134, 237, 186, 238, 184, 166, 74, 196, 189, 20, 172, 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